Description

Roles

Attributes

Steps

1. Gather information:

   Use various techniques to make gathering requirements easier. Face-to-face meetings with stakeholders is the most effective way to understand stakeholder needs and to gather and validate requirements, but you must prepare in order for these meetings to run efficiently.

    

   Be prepared by gathering and reviewing information related to the problem domain, problem statement, business environment and key stakeholders. Most of this information should be available in the Vision. Review the Work Items List for stakeholder requests.

2. Identify and capture domain terms:

   Collaborate with stakeholder to make sure that ambiguous or domain-specific terms are clearly defined in the Glossary and that you use these terms consistently.

3. Identify the types of requirements relevant to your system:

   Requirements can be broadly classified as either functional or non-functional requirements. The former specify what the system must do. The latter specify constraints on the solution such as usability, reliability, performance, supportability, interfaces with legacy systems, etc. Depending upon the domain there may be regulatory requirements that apply.

    

   Collaborate with stakeholders to identify the types of requirements relevant to your system. This will help you assess the completeness of your requirement set.

4. Identify and capture Use Case and Actors in a Use-Case Model:

   Collaborate with stakeholders to identify and capture the Actors and Use Cases in the Use-Case Model.

5. Identify and capture Supporting Requirements:

   Collaborate with stakeholders to identify and capture the other types of requirements relevant to your system.

6. Achieve concurrence:

   Conduct a review of the requirements with relevant Stakeholdersand the development team to ensure consistency with the Vision, assess quality, and identify any required changes.

7. Update the Work Items List:

   Capture references to the requirements in the Work Items List, so they can be prioritized.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Glossary			(none)
Supporting Requirements Specification			(none)
Use Case			(none)
Use-Case Model			(none)
Vision			(none)
Work Items List			(none)

Other Instances

Instance Parent
Enterprise OpenUP (with CobiT)Inception Iteration [1..n]Identify and Refine Requirements (Inception Iteration [1..n])
Enterprise OpenUP (with CobiT)Elaboration Iteration [1..n]Identify and Refine Requirements (Elaboration Iteration [1..n])